; * doc/lispref/tips.texi: Fix typo.

diff --git a/doc/lispref/tips.texi b/doc/lispref/tips.texi
index 6292054d306e897ac4192f4fa84efeb20dfa1211..1826e8f7b42a44fb4df9ca417b72a4e793a3cda1 100644 (file)
--- a/doc/lispref/tips.texi
+++ b/doc/lispref/tips.texi
@@ -956,7 +956,7 @@ multiple sub-sections.  Even though that was the only recommended
 approach for a long time, many people have chosen to use multiple
 top-level code sections instead.  You may chose either style.
 
-Using multiple top-level code sections has the advanatage that it
+Using multiple top-level code sections has the advantage that it
 avoids introducing an additional nesting level but it also means that
 the section named @samp{Code} does not contain all the code, which is
 awkward.  To avoid that, you should put no code at all inside that